|
|
 |
|
|
|
|
4. True or False: To build a sound, reusable subsystem of business classes, especially in a distributed architecture such as is typical in large, modern organizations, takes a small amount of time. |
|
|
|
|
|
|
|
|
False. To build a sound, reusable subsystem of business classes, especially in a distributed architecture such as is typical in large, modern organizations, takes considerable time. In fact, the bulk of the time consumed on software development projects is in the elaboration of the logic incorporated in business classes. All non-policy subsystems are pretty standard and highly reusable almost immediately upon implementing them. However, business classes are defined from a number of sources, including the memory and experiences of employees. Designing and implementing the Business Rules Subsystem, therefore, requires great patience on the part of the Visual Basic development staff. |
|
|
|
|
|
|
|
|
5. What is tricky about developing business classes in an environment that uses a relational database? |
|
|
|
|
|
|
|
|
Developing business classes with relational databases as part of the architecture of your environment can be tricky. Object databases don't require a separation of data from the objects themselves. However, relational databases, which still dominate the market, do require data disassembly. The problem then becomes how to effectively get the data out of business classes and into relational databases without compromising encapsulation rules? The bulk of the answer lies in design patterns. Day 19, The Database Access Subsystem, introduces you to some patterns/mechanisms for handling data in business classes using Visual Basic. |
|
|
|
|
|
|
|
|
1. What are pivotal class methods for the three reporting mechanisms discussed in this lesson? |
|
|
|
|
|
|
|
|
The pivotal class methods for these three reporting mechanisms include those operations that open the report, print the report, and save the report. These operations are members of an interface class, IReporting. |
|
|
|
|
|
|
|
|
2. What is the benefit of using Microsoft Access for reporting? |
|
|
|
|
|
|
|
|
Microsoft Access offers a very powerful and easy-to-use object library for creating, modifying, and deleting reports. Although you can certainly create and delete Access reports through the Active X object library via Visual Basic, it's easier to create the reports in Access itself if you and your users have a copy of it. Access 95, 97, and beyond make it easy to create reports with its report wizards. |
|
|
|
|
|